Skip to content

fix(android): support HTTP URLs in read#20

Merged
lodev09 merged 4 commits into
mainfrom
fix/android-http-url-read
Feb 8, 2026
Merged

fix(android): support HTTP URLs in read#20
lodev09 merged 4 commits into
mainfrom
fix/android-http-url-read

Conversation

@lodev09

@lodev09 lodev09 commented Feb 8, 2026

Copy link
Copy Markdown
Owner

Summary

Fixes #5. Android read() now supports HTTP/HTTPS URLs. Previously, ContentResolver.openInputStream() only handled content:// and file:// URIs, silently returning null for remote URLs. iOS worked out of the box via CGImageSourceCreateWithURL.

Also adds proper error handling on both platforms — errors now reject with descriptive messages and surface in LogBox via RCTLogWarn (iOS) and RNLog.w (Android) instead of silently resolving null.

Type of Change

  • Bug fix

Test Plan

  • Added URL input button in example app (using react-native-true-sheet)
  • Tested with remote GPS-tagged JPEG
  • Tested with invalid URIs — errors show in LogBox
  • Verified existing file:// and content:// URIs still work

Checklist

  • I tested on iOS
  • I tested on Android
  • I updated the documentation (if needed)

@lodev09 lodev09 merged commit 9d3a1fc into main Feb 8, 2026
3 checks passed
@lodev09 lodev09 deleted the fix/android-http-url-read branch February 8, 2026 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Getting null in Android when checking exif data

1 participant